Managing Data Across a Semantic Data View and a Presentation Data View

ABSTRACT

Managing data across a semantic data view and a presentation data view may be provided. A semantic model may be represented in a semantic data view and a presentation model may be represented in a presentation data view. The presentation model may correspond to a graphical representation of the semantic model. In addition, a command may be received directed toward the semantic data view or the presentation data view. The semantic model and the presentation model may be operated upon according to the received command. Furthermore, the semantic model represented in the semantic data view and the presentation model represented in the presentation data view may be updated in response to operating on the semantic model and the presentation model according to the received command. The semantic model and the presentation model may be simultaneously maintained in a volatile memory in a computer.

RELATED APPLICATIONS

This application is a Continuation of co-pending U.S. application Ser. No. 11/496,281 entitled “Managing Data Across a Semantic Data View and a Presentation Data View” filed Jul. 31, 2006, which is related to U.S. patent application Ser. No. 11/496,521, filed Jul. 31, 2006, entitled “Wrapping Nodes in a Drawing Canvas,” which are hereby incorporated by reference.

BACKGROUND

Visual aids help people understand information. Conveying information to or among groups of people may require creating visual presentations embodying the information. Graphics application programs, such as the Microsoft® PowerPoint® presentation application, have helped automate creating such visual presentations. Such graphics application programs allow users to convey information more efficiently and effectively by putting that information in an easily understandable format.

A graphic is a visual idea representation, such as a diagram or other drawing. A graphic is typically composed of several graphical elements (e.g. shown in a presentation data view) that represent content embodying the idea, such as, for example, a bulleted list (e.g. shown in a semantic data view). Each graphical element is a part of the displayed graphic. A graphical element can have both textual characteristics and graphical characteristics. Graphical characteristics generally refer to pictorial or other graphical element visual features. Textual characteristics generally refer to the written matter within the graphical element. Depending on the information and the audience, a graphics application program user generally determines a specific graphic that will best teach or convey the underlying information.

In some situations, the user may need to know whether they have an element selected in the semantic data view or the presentation data view because commands may work on only a subset of the presentation or semantic data visible in one of the views. Consequently, confusion may result because the user does not see updates in both locations (e.g. the semantic data view and the presentation data view). Thus, the conventional strategy does not allow the user to see how commands may apply to their presentation and semantic data simultaneously. Furthermore, the conventional strategy does not enable the user to see semantic and presentation data both selected at the same time, so that the user can more easily match the data between the views.

SUMMARY

Managing data across a semantic data view and a presentation data view may be provided. This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter. Nor is this Summary intended to be used to limit the claimed subject matter's scope.

Managing data across a semantic data view and a presentation data view may be provided. A semantic model may be represented in a semantic data view and a presentation model may be represented in a presentation data view. The presentation model may correspond to a graphical representation of the semantic model. In addition, a command may be received directed toward the semantic data view or the presentation data view. The semantic model and the presentation model may be operated upon according to the received command. Furthermore, the semantic model corresponding to the semantic data view and the presentation model corresponding to the presentation data view may be updated in response to operating on the semantic model and the presentation model according to the received command. The semantic model and the presentation model may be simultaneously maintained in a volatile memory in a computer.

Both the foregoing general description and the following detailed description provide examples and are explanatory only. Accordingly, the foregoing general description and the following detailed description should not be considered to be restrictive. Further, features or variations may be provided in addition to those set forth herein. For example, embodiments may be directed to various feature combinations and sub-combinations described in the detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments of the present invention. In the drawings:

FIG. 1 shows a semantic model and a presentation model;

FIG. 2 shows a shape in a presentation data view having a multiple data set;

FIG. 3 shows tab navigation;

FIG. 4 shows a node selected in a presentation data view;

FIG. 5 shows a user switched focus to a semantic data view with a normal node selected in a presentation data view;

FIG. 6 shows selecting only transition shapes;

FIG. 7 shows selecting a combination of normal nodes and transition nodes;

FIG. 8 shows a selection in a semantic data view when a user switches focus to a semantic data view from a presentation data view;

FIG. 9 shows selection of shapes with contained children;

FIG. 10 shows continuous text selection;

FIGS. 11A through 11C show grouped composite shapes;

FIG. 12 is a flow chart of a method for managing data across a semantic data view and a presentation data view; and

FIG. 13 is a block diagram of a system including a computing device.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While embodiments of the invention may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the invention. Instead, the invention's proper scope is defined by the appended claims.

Managing data across a semantic data view and a presentation data view may be provided. For example, as shown in FIG. 1, both a semantic model (e.g. in a semantic data view 105) and a presentation model (e.g. in a presentation data view 110) associated with the semantic model may be provided. Semantic data view 105 may comprise, but is not limited to, a text pane. Moreover, presentation data view 110 may comprise, but is not limited to a drawing canvas. The semantic model may utilize different data attributes (e.g. properties). For example, the different data attributes may comprise, but are not limited to, a data hierarchy, color, size, margin, and style. The aforementioned are examples and other data attributes may be used.

Because embodiments of the invention include both a semantic and a presentation model that may be directly related to one another, embodiments of the invention may allow both presentation and semantic parts of the model to be selected. That selection may then be presented in any given view by rendering a highlight around an element, whether the element is a presentation element or semantic element. For example, if a listing of all of the transition elements in a graphic is displayed, then the selection could be used to determine which semantic transition elements should display selection highlights in that view. This could be a view in addition to the text pane view of the data. As a further example, another pane may display all of the images used in the diagram (this can be semantic information). The selection information could then be use to highlight the images that correspond to shapes that are selected in the drawing canvas. In yet another example, embodiments of the invention may include multiple simultaneous views that each display a different presentation of the same semantic data. Consequently, even if the shapes were different in each view, embodiments of the invention may have a way to meaningfully select elements in every view so that the user could tell that a shape in one view corresponds to a different shape in another view (for example, the bottom shape in the pyramid corresponds to the first shape in the process diagram).

Consistent with embodiments of the invention, users may not need to know whether they have an element selected in semantic data view 105 or presentation data view 110, because commands may work simultaneously in both places. To avoid confusion, the users may see any updates (as appropriate) in both locations (e.g. semantic data view 105 and presentation data view 110). Accordingly, both semantic data view 105 and presentation data view 110 may be maintained in a computer's memory. Furthermore, commands may be interpreted either through semantic data view 105 or presentation data view 110 equally. Moreover, as will be described in more detail below, embodiments of the invention may include the ability to tab through shapes in presentation data view 110 based on the semantic model shown in the semantic data view 105.

As shown in FIG. 1, both apple in semantic data view 105 and apple in presentation data view 110 may be selected. Both selections may be maintained in the computer's memory. Regardless of where the selection takes place (e.g. in either semantic data view 105 or presentation data view 110), commands can operate on both. For example, if the focus is in semantic data view 105 and a red shape fill option is selected, the corresponding shape in presentation data view 110 may be updated.

FIG. 2 shows a shape in presentation data view 110 having a multiple data set, for example, a first node 215. As shown in FIG. 2, both elements in first node 215 are selected in semantic data view 105. A corresponding shape 220 in presentation data view 110 may remain selected as long as either grape or apple is selected in first node 215 in semantic data view 105. Additionally, if a single node in semantic data view 105 was associated with two shapes in presentation data view 110, if either of those two shapes in presentation data view 110 is selected, that corresponding single node in semantic data view 105 may also be selected. Moreover, regardless of whether a customization is applied in presentation data view 110 or in semantic data view 105, a command associated with the customization may be acted against the drawing elements selected.

FIG. 3 shows tab navigation. For example, by pressing tab while in presentation data view 110, selection may move through the shapes in presentation data view 110 based on semantic ordering (i.e. the order shown in semantic data view 105). As shown in FIG. 3, selection may move from apple, to grape, to banana, to watermelon regardless of what order they were drawn in presentation data view 110. FIG. 4 shows a node 420 selected in presentation data view 110. Consequently, a corresponding selection 415 may appear in semantic data view 105 in an unfocused color. For example, if node 420 is selected in presentation data view 110, corresponding selection 415 may be selected in semantic data view 105. Because the focus is not on semantic data view 105, selection 415 in semantic data view 105 may be a disabled color. As shown in FIG. 5, if the user switches focus to semantic data view 105 with a normal node 520 selected in presentation data view 110, all of normal node 520's corresponding text 515 in semantic data view 105 may be selected. Consequently, selection handles corresponding to normal node 520 in presentation data view 110 may now be an unfocused color. Furthermore, if there multiple nodes selected in presentation data view 110 and the user switches focus, the text in all selected nodes in semantic data view 105 may be selected.

FIG. 6 shows selecting only transition shapes. For example, if any transition shape (e.g. transition shape 605) is selected in presentation data view 110, nothing may be selected in semantic data view 105. From here, if the user switches focus to semantic data view 105 (e.g. via the F6 key or clicking on the part of semantic data view 105 that contains the nodes), there may be no corresponding selection in semantic data view 105. As a result, the focus may revert to a default selection, for example, may be shown at the beginning of the text of the first node in semantic data view 105. If there are multiple transitions selected in presentation data view 110 and the user switches focus, an insertion point (IP) may also revert to a default setting. Consequently, FIG. 6 shows that selecting a transition in presentation data view 110 may result in no corresponding selection in semantic data view 105.

FIG. 7 shows selecting a combination of normal nodes and transition nodes. For example, if a multiple contiguous/discontiguous selection in presentation data view 110 contains nodes 715, 720, and 725 and transitions 730 and 735, a selection 740 in semantic data view 105 may only show the nodes selected. As shown in FIG. 7, node 720 is selected, as a result, selection 740 corresponds to node 720. As shown in FIG. 8, however, when the user switches focus to test pane 105 (e.g. pressing the F6 key), and may appear at the beginning of the text in corresponding semantic data view 105's selection 740. In other words, if the user selected a transition followed by a node, semantic data view 105 and presentation data view 115 may appear as shown in FIG. 7. When the user switches focus from presentation data view 110 to semantic data view 105, the IP may appear at the beginning of selection 740 because that is the first node in the corresponding semantic data view 105's selection (i.e. selection 740). Consequently, FIG. 8 shows a selection in semantic data view 105 when the user switches focus to semantic data view 105 from presentation data view 110.

FIG. 9 shows selection of shapes with contained children. For example, if a shape in presentation data view 110 is selected that contains multiple nodes (e.g. child nodes represented as a bulleted list), then all corresponding nodes in semantic data view 105 may be selected with a non-focus selection color. If the focus moves back to semantic data view 105, the corresponding nodes in semantic data view 105 may be selected with an in-focus selection color. If text in a shape 915 in presentation data view 110 should be selected, for example, by pressing F2 after shape 915 has been selected, then a focus switch to semantic data view 105 may also result in all the corresponding text being selected. When selecting shapes in presentation data view 110, the visible nodes may be selected and acted upon. For example, as shown in FIG. 9, there are parent transitions between: i) A and x; and ii) A and y, however transitions may not be rendered in the diagram shown in presentation data view 110. As a result, they may not be explicitly part of the selection as shown in FIG. 9. In other words, as shown in FIG. 9, shape 915 may be selected in presentation data view 110. All the nodes that are part of shape 915 may be automatically selected in semantic data view 105. This selection may be in gray as semantic data view 105 does not have the focus. Note that the selection visuals in FIG. 9 do not reflect the final design.

FIG. 10 shows continuous text selection. For example, if shapes 1015 and 1020 are selected in presentation data view 110 that respectfully map to nodes 1025 and 1030 appearing next to each other in semantic data view 105, then all such nodes may be selected. Consequently, if the focus moves to semantic data view 105 all corresponding nodes in semantic data view 105 may be selected. If the focus moves back to presentation data view 110, both shapes 1015 and 1020 in presentation data view 110 should still be selected. In other words, shapes 1015 and 1020 (i.e. shapes “A” and “B”) have been selected in presentation data view 110. Because all nodes contained in shapes 1015 and 1020 are continuous in semantic data view 105, all of the nodes may be selected.

FIGS. 11A through 11C show grouped composite shapes. For example, if several shapes in presentation data view 110 map to one node in semantic data view 105, then the selection may correspond to the group selection in presentation data view 110. In other words, composite shapes may be rendered as groups. For example, if a user drills down into a shape that is a sub-shape of a group via presentation data view 110, or if the user clicks into a node, the selection in semantic data view 105 may surround the nodes in that sub-shape while other shapes in the group remain deselected. Furthermore, if the user selects in semantic data view 105, the selection may show that particular node in presentation data view 110.

In presentation data view 110, the user may either select that shape that corresponds to the node, or, if multiple nodes are displayed in one shape, the selection of the shape that contains the node may be shown. If there are multiple shapes that correspond to one node, then selecting in semantic data view 105 may select the shape in which the node is. Conversely, if a shape contains multiple nodes and the user selects that shape in presentation data view 110, the selection in semantic data view 105 may contain all of those nodes. Consequently, if the user selects a shape that contains multiple nodes in presentation data view 110, then the user may change focus to semantic data view 105. As a result, the selection may not be updated in semantic data view 105 to the single node the user selects until the user moves the IP or types. For example, when the user clicks in presentation data view 110 (FIG. 11A). If the user drills into a group presentation data view 110, semantic data view 105's selection may be updated (FIG. 11B). Then the user may click into semantic data view 105 and may select a group (FIG. 11C).

FIG. 12 is a flow chart setting forth the general stages involved in a method 1200 consistent with an embodiment of the invention for managing data across a semantic data view and a presentation data view. Method 1200 may be implemented using a computing device 1300 as described in more detail below with respect to FIG. 13. Ways to implement the stages of method 1200 will be described in greater detail below. Method 1200 may begin at starting block 1205 and proceed to stage 1210 where computing device 1300 may maintain a representation of a semantic model in semantic data view 105. From stage 1210, where computing device 1300 maintains the representation of the semantic model in semantic data view 105, method 1200 may advance to stage 1220 where computing device 1300 may maintain a representation of a presentation model in presentation data view 110. The represented presentation model may correspond to a graphical representation of the semantic model. For example, as shown in FIG. 1, both apple in semantic data view 105 and apple in presentation data view 110 may be selected. Both selections may be maintained in a computer's memory (e.g. in computing device 1300 system memory 1304 as described in more detail below). Regardless of where the selection takes place (e.g. in either semantic data view 105 or presentation data view 110), commands can operate on both. For example, if an IP is in semantic data view 105 and a red shape fill option is selected, the corresponding shape in presentation data view 110 may be updated.

Once computing device 1300 maintains the representation of the presentation model in presentation data view 110 in stage 1220, method 1200 may continue to stage 1230 where computing device 1300 may receive a command directed toward semantic data view 105 or presentation data view 110 from a user via input devices 1312. After computing device 1300 receives the command directed toward semantic data view 105 or presentation data view 110 in stage 1230, method 1200 may proceed to stage 1240 where computing device 1300 may operate on the semantic model and the presentation model according to the received command. For example, FIG. 2 shows a shape in presentation data view 110 having a multiple data set, for example, first node 215. As shown in FIG. 2, both elements in first node 215 are selected in semantic data view 105. A corresponding shape 220 in presentation data view 110 may remain selected as long as either grape or apple is selected in first node 215 in semantic data view 105. Additionally, if a single node in semantic data view 105 was associated with two shapes in presentation data view 110, if either of those two shapes in presentation data view 110 is selected, that corresponding single node in semantic data view 105 may also be selected.

Consistent with embodiments of the invention, many other commands may be received and many other operations may be performed as described, for example, above with respect to FIG. 1 through FIG. 11C. More examples of commands and operations are described as follows. For example, selecting a shape in presentation data view 110 may select all corresponding nodes in semantic data view 105. In addition, selecting a node in semantic data view 105 may select all corresponding shapes in presentation data view 110.

Moreover, removing a node from a previous state may leave a shape selected in presentation data view 110 if other semantic nodes are still selected that correspond with that shape. For example, if “A” and “B” are displayed in a shape and “A”, “B”, and the shape are selected, removing “B” from the selection may leave the shape selected because “A” may still be selected.

In the previous example, a command may apply to semantic nodes, but depending on the command, it may or may not apply to the nodes displayed in a selected shape that are not selected. For example, if “A” and “B” are displayed in the selected shape, but only A is selected, the type of command may determine whether to apply to only “A”, or to apply to “A” and “B” both. Moreover the command may additionally apply to the shape, because the shape is selected. In other words, B is “implied” by the selection even though it is not selected. Once computing device 1300 operates on the semantic model and the presentation model according to the received command in stage 1240, method 1200 may then end at stage 1250.

An embodiment consistent with the invention may comprise a system for managing data across a semantic data view and a presentation data view. The system may comprise a memory storage and a processing unit coupled to the memory storage. The processing unit may be operative to maintain a semantic model in a semantic data view and a presentation model in a presentation data view. The presentation model may correspond to a graphical representation of the semantic model. The processing unit may be further operative to receive a command in one of the semantic data view and the presentation data view and to operate on the semantic model and the presentation model according to the received command.

Another embodiment consistent with the invention may comprise a system for managing data across a semantic data view and a presentation data view. The system may comprise a memory storage and a processing unit coupled to the memory storage. The processing unit may be operative to maintain a semantic model in a semantic data view. The semantic model may have at least one node including at least one sub-node. The processing unit may be operative to maintain a presentation model in a presentation data view. The presentation model may correspond to a graphical representation of the semantic model. The presentation model may include a shape corresponding to the at least one node. The presentation model may be configured to select the shape when at least one of the following are selected in the semantic data view: the at least one node and the at least one sub-node.

Yet another embodiment consistent with the invention may comprise a system for managing data across a semantic data view and a presentation data view. The system may comprise a memory storage and a processing unit coupled to the memory storage. The processing unit may be operative to maintain a semantic model in a semantic data view. The semantic model may have at least one node. In addition, the processing unit may be operative to maintain a presentation model in a presentation data view. The presentation model may correspond to a graphical representation of the semantic model. The presentation model may include at least two shapes corresponding to the at least one node. The presentation model may be configured to select the at least two shapes when the at least one node is selected in the semantic data view.

FIG. 13 is a block diagram of a system including computing device 1300. Consistent with an embodiment of the invention, the aforementioned memory storage and processing unit may be implemented in a computing device, such as computing device 1300 of FIG. 13. Any suitable combination of hardware, software, or firmware may be used to implement the memory storage and processing unit. For example, the memory storage and processing unit may be implemented with computing device 1300 or any of other computing devices 1318, in combination with computing device 1300. The aforementioned system, device, and processors are examples and other systems, devices, and processors may comprise the aforementioned memory storage and processing unit, consistent with embodiments of the invention.

With reference to FIG. 13, a system consistent with an embodiment of the invention may include a computing device, such as computing device 1300. In a basic configuration, computing device 1300 may include at least one processing unit 1302 and a system memory 1304. Depending on the configuration and type of computing device, system memory 1304 may comprise, but is not limited to, volatile (e.g. random access memory (RAM)), non-volatile (e.g. read-only memory (ROM)), flash memory, or any combination. System memory 1304 may include operating system 1305, one or more programming modules 1306, and may include a program data file 1307. Operating system 1305, for example, may be suitable for controlling computing device 1300's operation. In one embodiment, programming modules 1306 may include, for example, data management module 1320. Furthermore, embodiments of the invention may be practiced in conjunction with a graphics library, other operating systems, or any other application program and is not limited to any particular application or system. This basic configuration is illustrated in FIG. 13 by those components within a dashed line 1308.

Computing device 1300 may have additional features or functionality. For example, computing device 1300 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in FIG. 13 by a removable storage 1309 and a non-removable storage 1310. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. System memory 1304, removable storage 1309, and non-removable storage 1310 are all computer storage media examples (i.e. memory storage). Computer storage media may include, but is not limited to, RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store information and which can be accessed by computing device 1300. Any such computer storage media may be part of device 1300. Computing device 1300 may also have input device(s) 1312 such as a keyboard, a mouse, a pen, a sound input device, a touch input device, etc. Output device(s) 1314 such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used.

Computing device 1300 may also contain a communication connection 1316 that may allow device 1300 to communicate with other computing devices 1318, such as over a network in a distributed computing environment, for example, an intranet or the Internet. Communication connection 1316 is one example of communication media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” may describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media. The term computer readable media as used herein may include both storage media and communication media.

As stated above, a number of program modules and data files may be stored in system memory 1304, including operating system 1305. While executing on processing unit 1302, data management module 1320 may perform processes including, for example, one or more method 1700's stages as described above. The aforementioned process is an example, and processing unit 1302 may perform other processes. Other programming modules that may be used in accordance with embodiments of the present invention may include electronic mail and contacts applications, word processing applications, spreadsheet applications, database applications, slide presentation applications, drawing or computer-aided application programs, etc.

Generally, consistent with embodiments of the invention, program modules may include routines, programs, components, data structures, and other types of structures that may perform particular tasks or that may implement particular abstract data types. Moreover, embodiments of the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. Embodiments of the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

Furthermore, embodiments of the invention may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. Embodiments of the invention may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies. In addition, embodiments of the invention may be practiced within a general purpose computer or in any other circuits or systems.

Embodiments of the invention, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process. Accordingly, the present invention may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). In other words, embodiments of the present invention may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. A computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific computer-readable medium examples (a non-exhaustive list), the computer-readable medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, and a portable compact disc read-only memory (CD-ROM). Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

Embodiments of the present invention, for example, are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to embodiments of the invention. The functions/acts noted in the blocks may occur out of the order as shown in any flowchart. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.

While certain embodiments of the invention have been described, other embodiments may exist. Furthermore, although embodiments of the present invention have been described as being associated with data stored in memory and other storage mediums, data can also be stored on or read from other types of computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or a CD-ROM, a carrier wave from the Internet, or other forms of RAM or ROM. Further, the disclosed methods' stages may be modified in any manner, including by reordering stages and/or inserting or deleting stages, without departing from the invention.

While the specification includes examples, the invention's scope is indicated by the following claims. Furthermore, while the specification has been described in language specific to structural features and/or methodological acts, the claims are not limited to the features or acts described above. Rather, the specific features and acts described above are disclosed as example for embodiments of the invention. 

1. A method for managing data across multiple data views, the method comprising: displaying a semantic data view pane comprising semantic nodes of a data model; displaying a presentation data view pane comprising presentation nodes of the data model, wherein each presentation node corresponds to at least one semantic node and wherein each semantic node corresponds to at least one presentation node; receiving a modification at one of: the semantic data view pane and the presentation data view pane; and updating, in response to the received modification, both the semantic data view pane and the presentation data view pane.
 2. The method of claim 1, further comprising displaying at least one sub-node of the data model, the at least one sub-node being represented in both the semantic data view pane and the presentation data view pane.
 3. The method of claim 2, further comprising: receiving a selection of at least one sub-node at either one of: the semantic data view pane and the presentation data view pane; and selecting all corresponding nodes associated with the selected at least one-sub node at the other one of: the semantic data view pane and the presentation data view pane.
 4. The method of claim 2, further comprising providing transitions between the at least one sub-node of the data model and a corresponding parent node of the data-mode.
 5. The method of claim 1, further comprising: receiving a selection of one of: the at least one semantic node and the least one presentation node; and selecting, in response the selection, the other one of: the at least one semantic node and the least one presentation node.
 6. The method of claim 1, further comprising: receiving a command at one of: the semantic data view pane and the presentation data view pane; and invoking the received command at the other one of: semantic data view pane and the presentation data view pane.
 7. The method of claim 6, further comprising: operating at the semantic data view pane and the presentation data view pane in response to the received command.
 8. A computer-readable medium comprising a set of instructions which when executed performs a method for managing data across multiple data views, the method executed by the set of instructions comprising: displaying a semantic data view comprising at least one semantic node; displaying a presentation data view comprising at least one shape associated with the at least one semantic node; providing at least one child node to the at least one shape, the at least one child node being associated with at least one sub-node displayed at the semantic data view; receiving a selection of at least one shape containing the at least one child node at the presentation data; and causing, in response to the received selection, a selection of the at least one semantic node and the at least one sub-node corresponding to the selected at least one shape.
 9. The computer-readable medium of claim 8, wherein causing the selection of the at least one semantic node and the at least one sub-node corresponding to the selected at least one shape comprises causing a non-focused selection of the at least one semantic node and the at least one sub-node corresponding to the selected at least one shape.
 10. The computer-readable medium of claim 8, further comprising grouping at least two shapes of the presentation data view into a composite shape.
 11. The computer-readable medium of claim 10, further comprising mapping the composite shape to a single node at the semantic data view.
 12. The computer-readable medium of claim 11, further comprising: receiving a selection of the single node at the semantic data view; and causing, in response to the selection, a selection of the at least two shapes at the presentation data view.
 13. The computer-readable medium of claim 10, wherein grouping the at least two shapes of the presentation data view into the composite shape comprises grouping at least one sub-shape with the at least one shape.
 14. The computer-readable medium of claim 8, further comprising: removing the at least one child node at the presentation data view; and maintaining the selection of the at least one semantic node corresponding to the at least one shape having its at least one child node removed.
 15. A system for managing data across multiple data views, the system comprising: a memory storage; and a processing unit coupled to the memory storage, the processing unit being configured to: display a semantic data view pane comprising semantic nodes of a data model; display a presentation data view pane comprising presentation nodes of the data model, wherein each presentation node corresponds to at least one semantic node and wherein each semantic node corresponds to at least one presentation node; provide at least one sub-node of the data model, the at least one sub-node being represented in both the semantic data view pane and the presentation data view pane; receive a selection of at least one sub-node at either one of: the semantic data view pane and the presentation data view pane; and cause a selection of all corresponding nodes associated with the selected at least one-sub node at the other one of: the semantic data view pane and the presentation data view pane.
 16. The system of claim 15, wherein the processing unit is further configured to: receive a selection of one of: the at least one semantic node and the least one presentation node; and select, in response the selection, the other one of: the at least one semantic node and the least one presentation node.
 17. The system of claim 15, wherein the processing unit is further configured to: receive a command at one of: the semantic data view pane and the presentation data view pane; and invoke the received command at the other one of: semantic data view pane and the presentation data view pane.
 18. The system of claim 17, wherein the processing unit is further configured to: operate at the semantic data view pane and the presentation data view pane in response to the received command.
 19. The system of claim 15, wherein the processing unit is further configured to: receive a modification at one of: the semantic data view pane and the presentation data view pane; and update, in response to the received modification, both the semantic data view pane and the presentation data view pane.
 20. The system of claim 15, wherein the processing unit being configured to cause the selection of all the corresponding nodes associated with the selected at least one-sub node comprises the processing unit being configured to cause an unfocused selection of all the corresponding nodes associated with the selected at least one-sub node. 